docs(research): record the portable package host test results - #548

Summary

Records the execution of the portable package host test (Wave item 4) under the protocol merged in #547, and routes the validation strategy to it. All real calls are done; no further execution is part of this PR.

Authorization and Governing Records

• Delivery Wave entry "Windows Portable Package, Local Build and Test", item 4, owner risk decisions and circuit-breaker limits.
• Protocol docs/research/experiments/portable-package-host-test.md as merged at 6f7fadb (docs(research): add the portable package host test protocol #547); execution bound that commit.
• Work carrier: Windows packaging and release pipeline #506.

Scope and Non-Goals

• Results section of the protocol record; one routing sentence in the validation strategy.
• No product change, no publication of either zip, no support or deployment claim.

Record-System Impact

• docs/research/experiments/portable-package-host-test.md (Results).
• docs/validation/strategy.md (routing sentence).

Evidence and Reasoning

• Build: audited WSL restore 0 warnings / 0 errors; public-release build 0.1.0-alpha.18+6f7fadbafa; every packaging check passed; package and symbols zip hashes recorded.
• Calls: 17 counted (6 I, 11 N). Silent success and fresh-process reuse passed for both roles and callers; interaction-required passed for personal native (not reached elsewhere); force-interactive success passed for both roles and callers.
• Deviations: Establish the Public Build and Dependency Baseline #1 is an in-protocol failed attempt (launcher ledger write; diagnosis recorded before Establish the Repository Record and Governance System #2). research: contract public-build evidence to a semantic singleton #7/research: record semantic WSL2 public-build observation #8 (WSL launcher failure, research: record semantic WSL2 public-build observation #8 started without a diagnosis) and running work WSL A/C before work native D are deviations. Target the Issue #1 public-build run at WSL2 #5 fired the "cannot identify a prompt" stop condition; continuing with Record the first Issue #1 WSL2 run receipt #6–Establish the AzureAuth Unofficial V2 Public Project Name #17 and the manual minimize step before Record the first Issue #1 WSL2 run receipt #6 are deviations. The owner admitted #2–#17 as evidence and ended the experiment.
• Limits: existing-state, one host, locally built archive (no Mark of the Web), development tools installed.

Identity and Security Effects

Token acquisition for the two existing accounts; WAM state updated and retained. No token, email, tenant, provider text, screenshot or crash dump in the record (checked with gitleaks and an email grep).

Validation

hk check --all passed.

Review and Disposition

Accepted target-branch authorities used: `origin/main-v2` (`6f7fadb`) AGENTS.md, governance policies, `controls.yaml`, the experiment policy, the accepted protocol and both review Skills.

• Independent review (rv_wave_pkg) on 1da01c4: record-system-review no material findings; research-evidence-review two blocking owner escalations and five advisories.
• Independent triage (tr_wave_pkg):
  • RE-R1 (launcher failures and call order): true positive (8/10). Establish the Public Build and Dependency Baseline #1 is an in-protocol failed attempt (diagnosis written before Establish the Repository Record and Governance System #2); research: contract public-build evidence to a semantic singleton #7/research: record semantic WSL2 public-build observation #8 and Reconcile and Baseline the V2 Product Requirements #14/docs(project): authorize requirements baseline review #15 before docs(requirements): reconcile v2 product baseline #16 are deviations; triage also found the after-call process checks of Establish the Public Build and Dependency Baseline #1, research: contract public-build evidence to a semantic singleton #7, research: record semantic WSL2 public-build observation #8 were not captured.
  • RE-R2 (Target the Issue #1 public-build run at WSL2 #5): record-keeping true positive (7/10); whether the stop condition fired was unresolved and needed the owner.
  • Advisories (allowlist, readiness answers, authority class, Ubuntu version, launcher fixes, inference label, strategy wording): true positive.
• Owner disposition: comment. Establish the Repository Record and Governance System #2–Establish the AzureAuth Unofficial V2 Public Project Name #17 admitted as evidence; Target the Issue #1 public-build run at WSL2 #5 treated as the "cannot identify a prompt" stop condition; no remaining WAM window after Target the Issue #1 public-build run at WSL2 #5; Establish repository governance and the public-build record gate #3 description admitted; experiment ended.
• Fixes: 7b48069 classifies every event, records the disposition, labels inferences, adds missing fields and narrows the strategy sentence.
• Rechecks: RECHECK-003/005 evaluated in docs(research): add the portable package host test protocol #547, unchanged; RECHECK-007 and RECHECK-008 evaluated in the record; others do not fire; release-triggered entries deferred.
• Re-review on 7b48069: RE-R1, RE-R2 and the advisories resolved; three new advisories, triaged true positive with no new owner decision: R-1 (record links to the PR, not the disposition comment), R-2 (this description's Deviations bullet used the old framing), R-3 (continuing after the Target the Issue #1 public-build run at WSL2 #5 stop and the minimize step not labeled as deviations). Fixed in 4fe9dc5 and this description.
• Re-review on 4fe9dc5: R-1, R-2 and R-3 resolved; no material findings under either Skill.

Upstream Provenance

None.